Send different decoded MID event types to different specs#6930
Conversation
dstocco
force-pushed
the
splitevents
branch
2 times, most recently
from
494d971 to
7dd6888
Compare
|
Hi @aphecetche , |
|
@dstocco I guess the idea then would be to ask for a QC tag, right @Barthelemy ? |
|
Well, I see that the v1.28 was produced yesterday. So I guess it's just a matter of moving to the new tag in the CI... |
|
@dstocco you can also put back the old file, and then remove it when the QC will have correct version. |
|
@shahor02 : good point, I've just done it |
|
@shahor02 can this one be merged ? thanks. |
3 participants
During data taking MID receives software calibration triggers that are used to test noisy channels.
Few BCs after the reception of the calibration trigger, the MID returns a special event (Front-End-Test event) where all channels should anwer.
These events are used to test the dead channels.
These events are not reconstructed like the physics event, but are sent to separate workflows and used to generate masks.
Since they're not used in the standard reconstruction, they will be streamed on different specs to simplify operations.
The commits are meant to be atomic. Please do not squash.